Method and System for Routing Transactions to a Mobile-Commerce Platform

ABSTRACT

A method and system for routing transactions to a mobile-commerce platform is described. One illustrative embodiment receives, via a network, a purchase request from a user&#39;s mobile communication device; authenticates the user to the mobile-commerce platform; generates a one-time-use perishable transaction code associated with the purchase request; prefixes to the transaction code an Issuer Identification Number (IIN) corresponding to the mobile-commerce platform to form a combined number; returns the combined number to the user&#39;s mobile communication device via the network to enable the user to provide the combined number to a merchant&#39;s point-of-sale system in connection with a transaction corresponding to the purchase request; and receives, via a payment network in communication with the merchant&#39;s point-of-sale system, the transaction code and transaction details associated with the transaction, the IIN informing the payment network to route the one-time-use perishable transaction code and the transaction details to the mobile-commerce platform.

PRIORITY

The present application claims priority from commonly owned and assignedU.S. Provisional Patent Application No. 61/248,767, Attorney Docket No.MOCA-006/00US, filed Oct. 5, 2009, entitled Method and System forRouting Transactions to a Mobile-Commerce Platform, which isincorporated herein by reference in its entirely and for all purposes.

FIELD OF THE INVENTION

The present invention relates generally to electronic commerce. Inparticular, but not by way of limitation, the present invention relatesto methods and systems for routing transactions to a mobile-commerceplatform.

BACKGROUND OF THE INVENTION

Mobile-commerce platforms permit consumers to purchase goods or servicesfrom merchants using a wireless mobile device such as a cellulartelephone. Some mobile-commerce platforms require merchants to installadditional software in their point-or-sale (POS) systems to permitdirect communication between the POS systems and the mobile-commerceplatform over a network.

Some merchants, particularly larger merchants with many stores, are notalways willing to install the necessary software in their POS systems tosupport such mobile-commerce platforms. This prevents consumers frommaking purchases via the mobile-commerce platform at some of the mostwell-known merchants. There is thus a need in the art to overcome thislimitation.

SUMMARY OF THE INVENTION

Illustrative embodiments of the present invention that are shown in thedrawings are summarized below. These and other embodiments are morefully described in the Detailed Description section. It is to beunderstood, however, that there is no intention to limit the inventionto the forms described in this Summary of the Invention or in theDetailed Description. One skilled in the art can recognize that thereare numerous modifications, equivalents, and alternative constructionsthat fall within the spirit and scope of the invention as expressed inthe claims.

The present invention can provide a method and system for routingtransactions to a mobile-commerce platform. One illustrative embodimentis a system for routing transactions to a mobile-commerce platform,comprising at least one processor; and a memory connected with the atleast one processor, the memory containing a plurality of programinstructions configured to cause the at least one processor to: receive,via a network, a purchase request from a user's mobile communicationdevice; authenticate the user to the mobile-commerce platform; generatea one-time-use perishable transaction code associated with the purchaserequest; prefix to the one-time-use perishable transaction code anIssuer Identification Number (IIN) to form a combined number, the IINcorresponding to the mobile-commerce platform; return the combinednumber to the user's mobile communication device via the network toenable the user to provide the combined number to a merchant'spoint-of-sale system in connection with a transaction corresponding tothe purchase request; and receive, via a payment network incommunication with the merchant's point-of-sale system, the one-time-useperishable transaction code and transaction details associated with thetransaction corresponding to the purchase request, the IIN informing thepayment network to route the one-time-use perishable transaction codeand the transaction details to the mobile-commerce platform.

Another illustrative embodiment is a computer-server-based method forrouting transactions to a mobile-commerce platform, comprisingreceiving, via a network at the computer server, a purchase request froma user's mobile communication device, wherein the computer server ispart of the mobile-commerce platform; authenticating the user to themobile-commerce platform; generating a one-time-use perishabletransaction code associated with the purchase request; prefixing to theone-time-use perishable transaction code an Issuer Identification Number(IIN) to form a combined number, the IIN corresponding to themobile-commerce platform; returning the combined number to the user'smobile communication device via the network to enable the user toprovide the combined number to a merchant's point-of-sale system inconnection with a transaction corresponding to the purchase request; andreceiving, via a payment network in communication with the merchant'spoint-of-sale system, the one-time-use perishable transaction code andtransaction details associated with the transaction corresponding to thepurchase request, the IIN informing the payment network to route theone-time-use perishable transaction code and the transaction details tothe mobile-commerce platform.

Yet another illustrative embodiment is a computerized method for routingtransactions to a mobile-commerce platform, comprising communicatingwith the mobile-commerce platform via a network using a mobilecommunication device to request a one-time-use perishable transactioncode in connection with a purchase from a merchant; receiving, at themobile communication device, a combined number from the mobile-commerceplatform, the combined number including an Issuer Identification Number(IIN) and the one-time-use perishable transaction code, wherein the IINis a prefix to the one-time-use perishable transaction code and the IINcorresponds to the mobile-commerce platform for transaction-routingpurposes; and providing the combined number to the merchant'spoint-of-sale system.

The methods of the invention can also be embodied, at least in part, ina plurality of program instructions executable by at least one processorthat are stored on a computer-readable storage medium.

These and other embodiments are described in further detail herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Various objects and advantages and a more complete understanding of thepresent invention are apparent and more readily appreciated by referenceto the following Detailed Description when taken in conjunction with theaccompanying Drawings, wherein:

FIG. 1 is a functional block diagram of an environment in which variousillustrative embodiments of the invention can be implemented;

FIG. 2 is functional block diagram of a mobile-payment configuration inwhich a merchant point-of-sale (POS) system is in direct communicationwith a mobile-commerce platform;

FIG. 3 is a functional block diagram of a mobile-payment configurationin which a merchant POS system and a mobile-commerce platform are not indirect communication in accordance with an illustrative embodiment ofthe invention;

FIG. 4A is a diagram showing a combined Issuer Identification Number(IIN) and transaction code in accordance with an illustrative embodimentof the invention;

FIG. 4B is a diagram showing a combined Issuer Identification Number(IIN) and transaction code in accordance with another illustrativeembodiment of the invention;

FIG. 5 is a functional block diagram of a computer server that hosts amobile-commerce application suite in accordance with an illustrativeembodiment of the invention;

FIG. 6A is a flowchart of a method for routing transactions to amobile-commerce platform in accordance with an illustrative embodimentof the invention;

FIG. 6B is a flowchart of a method for routing transactions to amobile-commerce platform in accordance with another illustrativeembodiment of the invention; and

FIG. 7 is a flowchart of a method for routing transactions to amobile-commerce platform in accordance with yet another illustrativeembodiment of the invention.

DETAILED DESCRIPTION

In various illustrative embodiments of the invention, the lack of adirect connection between a merchant's point-of-sale (POS) system and amobile-commerce platform is overcome by preceding the mobile-commerceplatform's one-time-use perishable transaction codes with anInternational Organization for Standardization (ISO) IssuerIdentification Number (IIN). The consumer provides the combined IIN andtransaction code to the merchant's POS system like a typical credit ordebit card number, and the IIN enables the transaction to be routed tothe mobile-commerce platform correctly via existing payment networks.

Referring now to the drawings, where like or similar elements aredesignated with identical reference numerals throughout the severalviews, and referring in particular to FIG. 1, it is a functional blockdiagram of an environment 100 in which various illustrative embodimentsof the invention can be implemented. Environment 100 includes network115, which interconnects one or more merchants 120, one or more wirelesscarriers 110 (e.g., SPRINT, T-MOBILE, AT&T, etc.), and mobile-commerceplatform 125. In some embodiments, network 115 includes, but is notnecessarily limited to, the Internet. Merchant 120 sells goods,services, or both at traditional brick-and-mortar stores, on-line, orboth at traditional brick-and-mortar stores and on-line.

Mobile device 105 associated with a particular user can communicate withthe various nodes of network 115 via wireless carrier 110. Specifically,the user can use mobile device 105 to purchase goods or services from amerchant 120 by interacting with mobile-commerce platform 125 overnetwork 115 in a manner that will be explained below. Depending on theparticular embodiment, mobile device 105 can be a cellular telephone,Personal Communication Service (PCS) phone, Personal Digital Assistant(PDA), or other portable communication device.

FIG. 2 is functional block diagram of a mobile-payment configuration 200in which a merchant POS system 215 is in direct communication with amobile-commerce platform 225. In this configuration, the merchant hascooperated in installing software (e.g., an application programminginterface or “API”) in its POS system to support such directcommunication with the mobile-commerce platform. Though the presentinvention concerns configurations in which such direct communicationbetween the merchant's POS and the mobile-commerce platform is notavailable, the configuration shown in FIG. 2 is discussed first to laythe groundwork for a clearer understanding of the invention and itsoperation. In the discussion of FIG. 2 that follows, the variousinteractions among the parts of mobile-payment configuration 200 areidentified by their corresponding reference numerals in parentheses.

Referring now to FIG. 2, mobile-device user 205 can use a variety ofdifferent access methods such as Short Message Service (SMS) messages,Multimedia Message Service (MMS) messages, Wireless Access Protocol(WAP), an application, or voice to obtain one-time-use perishabletransaction codes (hereinafter “transaction codes”) from mobile-commerceplatform 225 in making payments to merchants using any of a variety ofdifferent tenders (220). Mobile-device user 205 can also use a varietyof methods, including the above examples, to provide a transaction codeto merchant POS 215 in making electronic purchases (210).

Merchant POS system 215 receives payment authorizations (230) frommobile-commerce platform 225, which communicates with various paymentsystems 235 in executing transactions (sales, credits, debits,transfers, etc.). Payment systems 235 typically include credit-card,debit-card, gift-card, and alternative-payment (e.g., PAYPAL) systems.

When mobile-device user 205 makes a purchase, mobile-device user 205contacts mobile-commerce platform 225 using any of a variety of accessmethods (e.g., SMS, MMS, WAP or other browser technology, application,voice), and mobile-commerce platform 225 authenticates mobile-deviceuser 205.

Mobile-commerce platform 225 provides mobile-device user 205 withtransaction codes (220) and balances for various tenders available tothat user. A given transaction code may be used only once in connectionwith a particular purchase, and it automatically expires (becomesinvalid) if it is not used within a predetermined period after the userreceives it. Mobile-device user 205 selects a specific tender (e.g.,gift card, credit card, debit card, PAYPAL, etc.) to be used in makingthe purchase. The mobile-payments-enabled merchant submits, frommerchant POS system 215, the transaction code provided by mobile-deviceuser 205 and the transaction amount to mobile-commerce platform 225.Mobile-commerce platform 225 approves the transaction based on themerchant identifier, the transaction amount, and recognition of thetransaction code. If everything checks out when mobile-commerce platform225 executes the transaction with the applicable entity among paymentsystems 235, mobile-commerce platform 225 transmits a returnauthorization (230) to the merchant's POS system 215, completing thetransaction.

Mobile-commerce platforms such as that just described above inconnection with FIG. 2 are described in greater detail in U.S. Pat. No.7,657,489, “Systems and Method for Secure Wireless PaymentTransactions”; and U.S. patent application Ser. No. 12/343,423, “Systemand Method for Distributing Mobile Gift Cards”; both of which areincorporated herein by reference (both were included as appendixes inU.S. Provisional Application Mo. 61/248,767, cited above in the“Priority” section).

FIG. 3 is a functional block diagram of a mobile-payment configuration300 in which a merchant POS system 310 and a mobile-commerce platform320 are not in direct communication in accordance with an illustrativeembodiment of the invention. In this case, the merchant 120 (see FIG. 1)has not cooperated with the owners of mobile-commerce platform 320 ininstalling software (e.g., an API) in its POS system 310 to supportdirect communication with mobile-commerce platform 320. As indicated inFIG. 3, however, the user's mobile device 305 can still communicatewirelessly via network 115 with mobile-commerce platform 320 as in theconfiguration discussed above in connection with FIG. 2. Therefore, theuser can still obtain transaction codes from mobile-commerce platform320.

In the embodiment shown in FIG. 3, merchant POS system is in directcommunication with processors and payments networks 315, as is typicalof most merchants. “Processors” (or “acquirers”) are third-partyentities that process credit- and debit-card transactions for merchants.Examples include, without limitation, BANK OF AMERICA and TRANSFIRST.Credit/debit card companies such as VISA, MASTERCARD, DISCOVER, andAMERICAN EXPRESS have their own payment networks to which suchthird-party processors can forward credit- or debit-card transactionsreceived from merchants. Such payment networks are, in turn,, connectedwith issuing banks (not shown in FIG. 3), in the case of VISA andMASTERCARD (banks are also involved in the case of DISCOVER and AMERICANEXPRESS, but those banks are not the credit- or debit-card issuers).

In the credit/debit-card industry, the leading digits of the accountnumber on the card, called the Issuer Identification Number (IIN),uniquely identifies the entity that issued the card and is used byacquirers/processors and payment networks to route transactions to thecorrect (issuing) entity over the network. IINs are assigned to issuinginstitutions in accordance with an International Organization forStandardization (ISO) standard. An IIN is typically six digits long. Theentire credit/debit-card account number is typically 16 digits long forVISA and MASTERCARD and 15-18 digits long for DISCOVER and AMERICANEXPRESS.

In the embodiment shown in FIG. 3, the owners of mobile-commerceplatform 320 have established business relationships with one or moreacquirers/processors and payment networks (VISA/MASTERCARD,DISCOVER/AMEX, etc.) to recognise an IIN that corresponds tomobile-commerce platform 320. This IIN permits transactions intended formobile-commerce platform 320 to be routed, via existing payment networks(see 315 in FIG. 3), from merchant POS system 310 to mobile-commerceplatform 320, thus obviating the need for direct communication betweenmerchant POS 310 and mobile-commerce platform 320. Such an arrangementserves to route transactions to mobile-commerce platform 320 even thoughmobile-commerce platform 320 might not itself be a card-issuing entity.

Referring to FIG. 4A, it is a diagram showing a combined IssuerIdentification Number (IIN) and transaction code (“combined number”) 400in accordance with an illustrative embodiment of the invention. When amobile-device user contacts mobile-commerce platform 320 to carry out apurchase from a merchant using mobile device 305, instead of returningto mobile device 305 just the transaction code discussed above inconnection with FIG. 2, mobile-commerce platform 320 adds the IIN 405corresponding to mobile-commerce platform 320 (symbolized as “AAAAAA” inFIG. 4A) to the transaction code 410 (symbolized as “XXXXXXXXXX” in FIG.4A) as a prefix. For example, in one embodiment a six-digit IIN 405 isadded as a prefix to a ten-digit transaction code 410 (one-time-useperishable transaction code used in approving transactions, as discussedabove) to produce a 16-digit combined number 400, as illustrated in FIG.4A.

Referring next to FIG. 4B, in other embodiments, different length IINsand transaction codes can be used, and combined number 400 can includeadditional components. For example, in the illustrative embodiment shownin FIG. 4B, a transaction code 410 of from 9 to 12 digits, inclusive, isemployed, and the last (rightmost) digit of combined number 400 is acheck digit 412 (symbolized as “Y” in FIG. 4B).

Referring again to FIG. 3, mobile-commerce platform 320, upon receivinga transaction routed to it via processors and payment networks 315 byvirtue of the added IIN 405 in combined number 400, communicates withpayment systems 325 to execute the transaction. The step-by-step processof carrying out a sales transaction is discussed in greater detail belowin connection with FIGS. 6A and 6B.

Referring next to FIG. 5, it is a functional block diagram of a computerserver (“server”) 500 that hosts a mobile-commerce application suite inaccordance with an illustrative embodiment of the invention. In thisembodiment, server 500 is part of mobile-commerce platform 320 (see FIG.3). In FIG. 5, processor 505 communicates over data bus 510 with inputdevices 515, display 520, communication interfaces (“COMM. INTERFACES”in FIG. 5) 525, storage devices 530 (e.g., hard disk drives or flashmemory), and memory 535. Though FIG. 5 shows only a single processor,multiple processors or a multi-core processor may be present in someembodiments.

Input devices 515 include, for example, a keyboard, a mouse or otherpointing device, or other devices that are used to input data orcommands to server 500 to control its operation. Communicationinterfaces 525 may include, for example, various serial or parallelinterfaces for communicating with network 115 (see FIG. 1) or one ormore peripherals.

Memory 535 may include, without limitation, random access memory (RAM),read-only memory (ROM), flash memory, magnetic storage (e.g., a harddisk drive), optical storage, or a combination of these, depending onthe particular embodiment. In FIG. 5, memory 535 includesmobile-commerce applications 540, which control and manage variousaspects of the operation of mobile-commerce platform 320. Equipped withmobile-commerce applications 540, server 500 implements a server-sidedigital wallet to support mobile payments by users equipped withappropriately configured mobile devices 305. Each such user has a secureaccount on server 500.

Mobile-commerce applications 540 may be divided into various functionalmodules, depending on the particular embodiment. FIG. 5 depicts merelyone example of how such functional modules can be identified. In otherembodiments, there may be more or fewer functional modules, and they maybe subdivided or combined differently or named differently in thoseother embodiments.

In FIG. 5, accounts-management module 545 manages user accounts,including the storage of user profile information and preferences andthe management of the various forms of tenders available to a givenuser. Transaction-code-generation module 550 generates transaction codes410. IIN module 555 adds the IIN 405 corresponding to mobile-commerceplatform 320 to a transaction code 410. Communication module 560 handlescommunications over network 115 between server 500 and other systemssuch as a user's mobile device 305, processors and payment networks 315,and payment systems 325.

In one illustrative embodiment, mobile-commerce applications 540 areimplemented as software that is executed by processor 505. Such softwaremay be stored, prior to its being loaded into RAM for execution byprocessor 505, on any suitable computer-readable storage medium such asa hard disk drive, an optical disk, or a flash memory. In general, thefunctionality of server 500 may be implemented using a combination ofhardware and software and/or firmware.

In some embodiments, server 500 is implemented using a single machine.In other embodiments, multiple machines are networked together toprovide the needed functionality and performance.

Referring next to FIG. 6A, it is a flowchart of a method 600 for routingtransactions to a mobile-commerce platform in accordance with anillustrative embodiment of the invention. Throughout the discussion ofFIG. 6A that follows, frequent reference will also be made to FIGS. 1and 3.

Method 600 begins with a mobile-device user contacting mobile-commerceplatform 320 via network 115 using a mobile device 305. At 605,mobile-commerce platform 320 receives the user's request to make apurchase from a merchant 120. At 610, mobile-commerce platform 320authenticates the user using, for example, an optional PIN and, in someembodiments, other factors such as the mobile communication deviceidentifier of mobile device 305. Mobile-commerce platform 320 at 615,generates a transaction code 410, as explained above. At 620,mobile-commerce platform 320 adds IIN 405 to transaction code 410 as aprefix to form combined number 400 (see FIGS. 4A and 4B). At 625,mobile-commerce platform 320 returns the combined number 400 to mobiledevice 305. As explained above, the IIN 405 forms the leadings digits ofthe combined number 400 so it can serve as a mechanism for identifyingmobile-commerce platform 320 and routing transactions to mobile-commerceplatform 320 via processors and payment networks 315.

Next, the user provides the combined number 400 (IIN 405 and transactioncode 410) to merchant POS system 310 by any of a variety of methods,including, without limitation, radio-frequency identification (RFID),WI-FI, BLUETOOTH, WIMAX, one or two-dimensional bar code (scanned fromthe display of mobile device 305), and voice (i.e., the user speakscombined number 400 to the merchant 120, who enters it into merchant POSsystem 310 using a keypad or other user interface).

Combined number 400 is transmitted from merchant POS system 310 toprocessors and payment networks 315. Based on the business relationshipsdiscussed above between the owners of mobile-commerce platform 320 andvarious processors and payment networks, processors and payment networks315 route the transaction to mobile-commerce platform 320. At 630,mobile-commerce platform 320 receives the transaction details (amount,merchant, etc.) and transaction code 410 from processors and paymentnetworks 315. Note that, in any given transaction, combined number 400will typically pass through one processor and one payment network orthrough only one payment network, where the merchant POS system 310 isdirectly connected with the VISA/MASTERCARD or DISCOVER/AMEX paymentnetwork. At 635, method 600 terminates.

Referring next to FIG. 6B, it is a flowchart of a method 638 for routingtransactions to a mobile-commerce platform in accordance with anotherillustrative embodiment of the invention. The embodiment shown in FIG.6B coincides with that shown in FIG. 6A through Block 630. Thus, theblocks preceding Block 630 in FIG. 6A have not been repeated in FIG. 6B.

At 640, mobile-commerce platform 320 bases approval of the receivedtransaction on the merchant identifier, the transaction amount, andrecognition of the transaction code 410. If the transaction is approved,mobile-commerce platform 320 communicates, at 645, with payment systems325 to execute the transaction in accordance with me particular tenderselected by the mobile-device user. If an authorization code (e.g.,“00”) comes back from the applicable payment system among paymentsystems 325 indicating that all is well with the transaction,mobile-commerce platform 320, at 650, transmits an authorization-code tothe applicable payment network (see processors and payment networks 315in FIG. 3), which forwards the authorization code to merchant POS system310, completing the transaction. At 655, method 638 terminates.

Referring next to FIG. 7, it is a flowchart of a method 700 for routingtransactions to a mobile-commerce platform 320 in accordance with yetanother illustrative embodiment of the invention. FIG. 7 depicts therouting of a transaction to mobile-commerce platform 320 from the pointof view of a mobile-device user making a purchase from a merchant 120.

At 705, the mobile-device user contacts mobile-commerce platform 320 vianetwork 115 using a mobile device 305, as explained above. At 710, themobile-device user receives the combined number 400 made up of IIN 405and transaction code 410 (see FIGS. 4A and 4B) at his or her mobiledevice 305. At 715, the mobile-device user provides the combined number400 to the merchant's POS system 310 like a typical credit or debit cardnumber, as explained above.

As explained above, the IIN 405 in combined number 400 enables thetransaction to be routed to mobile-commerce platform 320 via existingprocessors and payment networks 315, thereby overcoming the lack of adirect connection between merchant POS system 310 and mobile-commerceplatform 320. At 720, method 700 terminates.

In conclusion, the present invention provides, among other things, amethod and system for routing transactions to a mobile-commerceplatform. Those skilled in the art can readily recognize that numerousvariations and substitutions may be made in the invention, its use, andits configuration to achieve substantially the same results as achievedby the embodiments described herein. Accordingly, there is no intentionto limit the invention to the disclosed exemplary forms. Manyvariations, modifications, and alternative constructions fall within thescope and spirit of the disclosed invention.

1. A system for routing transactions to a mobile-commerce platform,comprising: at least one processor; and a memory connected with the atleast one processor, the memory containing a plurality of programinstructions configured to cause the at least one processor to: receive,via a network, a transaction request from a user's mobile communicationdevice; authenticate the user to the mobile-commerce platform; generatea one-time-use perishable transaction code associated with thetransaction request; append to the one-time-use perishable transactioncode an Issuer Identification Number (IIN) to form a combined number,the IIN corresponding to at least one tender associated with the user;return the combined number to the user's mobile communication device viathe network to enable the device to provide the combined number to asystem associated with a merchant in connection with a transactioncorresponding to the transaction request; and receive the one-time-useperishable transaction code and transaction details associated with thetransaction corresponding to the transaction request from the systemassociated with the merchant.
 2. The system of claim 1, wherein theplurality of program instructions are further configured to cause the atleast one processor to: approve the transaction based on a merchantidentifier, a transaction amount, and recognition of the receivedone-time-use perishable transaction code; communicate with a paymentsystem to execute the approved transaction in accordance with the atleast one tender; and transmit an authorization code to a paymentnetwork in response to receipt of an authorization code from the paymentsystem to enable the payment network to forward the transmittedauthorization code to the system associated with the merchant tocomplete the transaction.
 3. The system of claim 2, wherein the tenderis one of a credit card, a debit card, a gift card, and analternative-payment method.
 4. The system of claim 2, wherein thepayment system is one of a credit-card payment system, a debit-cardpayment system, a gift-card payment system, and an alternative-paymentsystem.
 5. The system of claim 1, wherein the user's mobilecommunication device is one of a cellular telephone, a PersonalCommunication Service (PCS) phone, and a Personal Digital Assistant(PDA).
 6. The system of claim 1, wherein the IIN is six digits long andthe combined number is at least 15 digits long.
 7. The system of claim1, wherein the mobile-commerce platform maintains an account for theuser, the system acting as a server-side digital wallet for at least onetender associated with the user.
 8. A computer-server-based method forrouting transactions to a mobile-commerce platform, thecomputer-server-based method comprising: receiving, via a network at thecomputer server, a transaction request from a user's mobilecommunication device, wherein the computer server is part of themobile-commerce platform; authenticating the user to the mobile-commerceplatform; generating a one-time-use perishable transaction codeassociated with the transaction request; appending to the one-time-useperishable transaction code an Issuer Identification Number (IIN) toform a combined number, the IIN corresponding to a tender associatedwith the user; returning the combined number to the user's mobilecommunication device via the network to enable the device to provide thecombined number to system associated with a merchant in connection witha transaction corresponding to the transaction request; and receivingthe one-time-use perishable transaction code and transaction detailsassociated with the transaction corresponding to the transaction requestfrom the system associated with the merchant.
 9. Thecomputer-server-based method of claim 8, further comprising: approvingthe transaction based on a merchant identifier, a transaction amount,and recognition of the received one-time-use perishable transactioncode; communicating with a payment system to execute the approvedtransaction in accordance with the at least one tender; and transmittingan authorization code to a payment network in response to receipt of anauthorization code from the payment system to enable the payment networkto forward the transmitted authorization code to the system associatedwith the merchant to complete the transaction.
 10. Thecomputer-server-based method of claim 9, wherein the tender is one of acredit card, a debit card, a gift card, and an alternative-paymentmethod.
 11. The computer-server-based method of claim 9, wherein thepayment system is one of a credit-card payment system, a debit-cardpayment system, a gift-card payment system, and an alternative-paymentsystem.
 12. The computer-server-based method of claim 8, wherein theuser's mobile communication device is one of a cellular telephone, aPersonal Communication Service (PCS) phone, and a Personal DigitalAssistant (PDA).
 13. The computer-server-based method of claim 8,wherein the IIN is six digits long and the combined number is at least15 digits long.
 14. The computer-server-based method of claim 8, whereinthe mobile-commerce platform maintains an account for the user, thecomputer server acting as a server-side digital wallet for at least onetender associated with the user.
 15. A computer-readable storage mediumcontaining a plurality of program instructions executable by at leastone processor to route transactions to a mobile-commerce platform, theplurality of program instructions being configured to cause the at leastone processor to: receive, via a network, a transaction request from auser's mobile communication device; authenticate the user to themobile-commerce platform; generate a one-time-use perishable transactioncode associated with the transaction request; append to the one-time-useperishable transaction code an Issuer Identification Number (IIN) toform a combined number, the IIN corresponding to at least one tenderassociated with the user; return the combined number to the user'smobile communication device via the network to enable the device toprovide the combined number to a system associated with a merchant inconnection with a transaction corresponding to the transaction request;and receive the one-time-use perishable transaction code and transactiondetails associated with the transaction corresponding to the transactionrequest from the system associated with the merchant.
 16. Thecomputer-readable storage medium of claim 15, wherein the plurality ofprogram instructions are further configured to cause the at least oneprocessor to: approve the transaction based on a merchant identifier, atransaction amount, and recognition of the received one-time-useperishable transaction code; communicate with a payment system toexecute the approved transaction in accordance with the at least onetender; and transmit an authorization code to a payment network inresponse to receipt of an authorization code from the payment system toenable the payment network to forward the transmitted authorization codeto the system associated with the merchant to complete the transaction.17. The computer-readable storage medium of claim 16, wherein the tenderis one of a credit card, a debit card, a gift card, and analternative-payment method.
 18. The computer-readable storage medium ofclaim 16, wherein the payment system is one of a credit-card paymentsystem, a debit-card payment system, a gift-card payment system, and analternative-payment system.
 19. The computer-readable storage medium ofclaim 15, wherein the user's mobile communication device is one of acellular telephone, a Personal Communication Service (PCS) phone, and aPersonal Digital Assistant (PDA).
 20. The computer-readable storagemedium of claim 15, wherein the IIN is six digits long and the combinednumber is at least 15 digits long.
 21. The computer-readable storagemedium of claim 15, wherein the mobile-commerce platform maintains anaccount for the user, a computer server associated with themobile-commerce platform acting as a server-side digital wallet for atleast one tender associated with the user.
 22. A computerized method forrouting transactions to a mobile-commerce platform, the computerizedmethod comprising: communicating with the mobile-commerce platform via anetwork using a mobile communication device to request a one-time-useperishable transaction code in connection with a transaction from amerchant; receiving, at the mobile communication device, a combinednumber from the mobile-commerce platform, the combined number includingan Issuer Identification Number (IIN) and the one-time-use perishabletransaction code, wherein the IIN is appended to the one-time-useperishable transaction code and the IIN corresponds to at least onetender associated with the user; and providing the combined number to asystem associated with the merchant.
 23. The computerized method ofclaim 22, wherein the IIN causes the one-time-use perishable transactioncode and transaction details associated with the purchase to be routedto the mobile-commerce platform via a payment network connected with thesystem associated with the merchant.
 24. The computerized method ofclaim 22, wherein the mobile-commerce platform maintains an account forthe user, a computer server associated with the mobile-commerce platformacting as a server-side digital wallet for at least one tenderassociated with the user.
 25. The computerized method of claim 24,wherein the at least one tender is one of a credit card, a debit card, agift card, and an alternative-payment method.
 26. The computerizedmethod of claim 22, wherein the mobile communication device is one of acellular telephone, a Personal Communication Service (PCS) phone, and aPersonal Digital Assistant (PDA).
 27. The computerized method of claim22, wherein the IIN is six digits long and the combined number is atleast 15 digits long.
 28. The system of claim 1, wherein the pluralityof program instructions are further configured to cause the at least oneprocessor to: receive the one-time use perishable transaction code froma payment network in communication with the system associated with themerchant.
 29. The system of claim 28, wherein the IIN informs thepayment network to route the one-time-use perishable transaction codeand the transaction details to the mobile-commerce platform.
 30. Themethod of claim 9, further comprising: receiving the one-time useperishable transaction code from a payment network in communication withthe system associated with the merchant.
 31. The method of claim 30,wherein the IIN informs the payment network to route the one-time-useperishable transaction code and the transaction details to themobile-commerce platform.